Payment and charging system using a medium and internet sites

ABSTRACT

This application relates to a payment and charging system using a medium and internet sites. In one aspect, the system uses a uniform resource locator (URL) medium and an internet site (vault site) for supporting a means of charging money into a URL vault (outside the URL medium), a means of paying with money of a URL vault, a payment means of various transactions or a various charging means. The described technology can provide a safer, more convenient and more economical means of payment and charging.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation application of International Patent ApplicationNo. PCT/KR2019/010504, filed on Aug. 19, 2019, which claims priority toKorean Patent Application No. 10-2018-0095861 filed on Aug. 17, 2018,contents of both of which are incorporated herein by reference in theirentireties.

BACKGROUND Technical Field

The described technology relates to a payment or charging system andmethod, using a medium, etc.

Description of Related Technology

(Types and overview of payment) There are RF card payment, URL-NFC-CC{refer to Korean Patent 10-2016-0063699 (KR No. 10-1751640) or10-2017-0096573 (KR No. 10-1941587)} payment, App&SP (Smartphone with anapp installed) payment, etc., and examples of the App&SP payment caninclude Alipay and WeChat Pay. These payments differ in the system andmethod of connecting the medium and the ‘storing money.’ These paymentsalso differ in the medium and the ‘storing money.’

SUMMARY

One aspect is a simpler and more economical means of payment orcharging.

Another aspect is a payment or charging method applicable to a widervariety of transactions.

Another aspect is a payment or charging method capable of structurallyblocking hacking.

Another aspect is a payment or charging method that can supportadditional services more economically.

Another aspect is a face-to-face transaction payment method and systemwithout a user confirmation (e.g., refer to FIG. 5 or 6). This is asystem and method in which a uniform resource locator (URL) medium, auser, a URL point of sale (POS), a VS, a URL vault, a collectionaccount, a payment request, a vault URL, URL POS info, a payment order,money, a payment order result, or a payment result, etc. operateorganically. The system and method pays with money outside of the URLmedium through the URL medium and the Internet site.

Another aspect is a payment method and system in a face-to-facetransaction that confirms a user after requesting a payment (e.g., referto FIG. 7 or 8). This is a system and method in which a URL medium, auser, a URL POS, a TD, a VS, a URL vault, a collection account, apayment request, a vault URL, URL POS info, a vault site, TD info, avault URL-PWD, a vault URL-PWD check result, order details, an orderconfirmation, a payment order, money, a payment order result, or apayment result, etc. operate organically. The system and method payswith money outside of the URL medium through the URL medium and theInternet site.

Another aspect is a payment method and system for a face-to-facetransaction requesting a payment after confirming a user (e.g., refer toFIG. 9 or 10). This is a system and method in which a URL medium, auser, a TD, a URL POS, a VS, a URL vault, a collection account, a vaultURL, a vault site, TD info, a vault URL-PWD, a vault URL-PWD checkresult, a payment reservation, a payment request, URL POS info, apayment order, money, a payment order result, or a payment result, etc.operate organically. The system and method pays with money outside ofthe URL medium through the URL medium and the Internet site.

Another aspect is a payment method and system for a non-face-to-facetransaction confirming a user after requesting a payment (e.g., refer toFIG. 11 or 12). This is a system and method in which a URL medium, auser, a TD, an SS, a VS, a URL vault, a collection account, an SS accessorder, a sales site, a payment request, an Order #, SS info, a vaultURL, a vault site, TD info, a vault URL-PWD, a vault URL-PWD checkresult, order details, an order confirmation, a payment order, money, apayment order result, or a payment result, etc. operate organically. Thesystem and method pays with money outside of the URL medium through theURL medium and the Internet site.

Another aspect is a payment method and system for an non-face-to-facetransaction requesting a payment after confirming a user (e.g., refer toFIG. 13 or 14). This is a system and method in which a URL medium, auser, a TD, an SS, a VS, a URL vault, a collection account, a vault URL,a vault site, TD info, a vault URL-PWD, a vault URL-PWD check result, apayment reservation, a SS access order, a sales site, a payment request,SS info, a payment order, money, a payment order result, or a paymentresult, etc. operate organically. The system and method pays with moneyoutside of the URL medium using the URL medium and the Internet site.

Another aspect is a payment method and system for face-to-facetransactions using two URL mediums without confirming a user (e.g.,refer to FIG. 15 or 16). This is a system and method in which a URLmedium-B, a URL medium-S, a user-B, a TD, a VS, a URL vault-B, acollection account-S, a vault URL-B, a vault site-B, TD info, a paymentrequest, a vault URL-S, a payment order, money, a payment order result,or a payment result, etc. operate organically. The system and methodpays with money outside of the URL medium-B using the two URL mediumsand the Internet site.

Another aspect is a payment method and system for face-to-facetransactions using two URL mediums, identifying a user (e.g., refer toFIG. 17 or 18). This is a system and method in which a URL medium-B, aURL medium-S, a user-B, a TD, a VS, a URL vault-B, a collectionaccount-S, a vault URL-B, a vault site-B, TD info, a vault URL-B-PWD, avault URL-B-PWD check result, a payment request, a vault URL-S, apayment order, money, a payment order result, or a payment result, etc.operate organically. The system and method pays with money outside ofthe URL medium-B through the two URL mediums and the Internet site.

Another aspect is a payment method and system for face-to-facetransaction through a provisional payment (e.g., refer to FIG. 19 or20). This is a system and method in which a URL medium, a user, a URLPOS, a payment request, a vault URL, or a payment result, etc. operateorganically. The system and method use the URL medium to pay with moneyoutside of the URL medium, and the type of the payment is theprovisional payment.

Another aspect is a non-face-to-face charging method and system afterconfirming a user (e.g., refer to FIG. 21 or 22). This is a system andmethod in which a URL medium, a user, a TD, a VS, a money supplier, aURL vault, a vault URL, a vault site, a vault URL-PWD, a vault URL-PWDcheck result, a charge request, a charge order, money, a charge orderresult, or a charge result, etc. operate organically. In the system andmethod, ‘the outside of the URL medium’ (URL vault) can be charged withmoney through the URL medium and the Internet site.

Another aspect is a face-to-face charging method and system in whichmoney is paid to a third party and the third party performs charging asan agent (e.g., refer to FIG. 23 or 24) This is a system and method inwhich a URL medium, a user, a URL POS, a VS, a money supplier, a URLvault, a charge agency request, a vault URL, URL POS info, a chargeorder, money, a charge order result, or a charge agency result, etc.operate organically. In the system and method, ‘the outside of the URLmedium’(URL vault) can be charged with money through the URL medium andthe Internet site.

Another aspect is a face-to-face charging method and system where a URLvault can be charged with a coupon generated by transaction, etc. (e.g.,refer to FIG. 25 or 26). This is a system and method in which a URLmedium, a user, a URL POS, a VS, a URL vault, a coupon charge request, avault URL, URL POS info, a coupon, or a coupon charge result, etc.operate organically. In the system and method, ‘the outside of the URLmedium’ (URL vault) can be charged with a coupon through the URL mediumand the Internet site.

Another aspect is a non-face-to-face charging method and system where aURL vault can be charged with a coupon generated by transaction, etc.(e.g., refer to FIG. 27 or 28). This is a system and method in which aURL medium, a user, a TD, a SS, a VS, a URL vault, a coupon chargerequest, URL medium info, SS info, a coupon, or a coupon charge result,etc. operate organically. In the system and method, ‘the outside of theURL medium’ (URL vault) can be charged with a coupon through the URLmedium and the Internet site.

Another aspect is an electronic payment system, comprising: a URL mediumthat can store a vault URL, etc., and deliver the vault URL to a URLPOS; the URL POS that can receive a payment request, etc. from a user,receive the vault URL from the URL medium, connect to a VS in responseto the vault URL, deliver URL POS info, or the payment request, etc. tothe VS, and deliver a payment result, etc. received from the VS to theuser; the VS that can connect to the URL POS in response to the vaultURL, receive the URL POS info, or the payment request, etc. from the URLPOS, deliver a payment order, etc. to a URL vault, receive a paymentorder result, etc. from the URL vault, and deliver the payment result,etc. to the URL POS; the URL vault that can receive the payment order,etc. from the VS, deliver a money to a collection account, and deliverthe payment order result, etc. to the VS; and the collection accountthat can collect the money.

Another aspect is an electronic payment method, comprising: step a) inwhich a URL POS receives a payment request, etc. from a user, receives avault URL from a URL medium, connects to a VS in response to the vaultURL, and delivers URL POS info, or the payment request, etc. to the VS;step b) in which the VS connects to the URL POS in response to the vaultURL, and delivers a payment order, etc. to a URL vault; step c) in whichthe URL vault delivers a money to a collection account; and step d) inwhich the collection account collects the money; the URL vault deliversa payment order result, etc. to the VS; the VS delivers a paymentresult, etc. to the URL POS; and the URL POS delivers the paymentresult, etc. to the user.

Another aspect is an electronic payment system, comprising: a URLmedium-B that can store a vault URL-B, etc., and deliver the vault URL-Bto a TD; a URL medium-S that can store a vault URL-S, etc., and deliverthe vault URL-S to the TD; the TD that can receive the vault URL-B fromthe URL medium-B, connect to a VS or a vault site-B in response to thevault URL-B, deliver TD info, etc. to the VS, deliver a payment request,etc. received from a user-B to the VS, receive the vault URL-S from theURL medium-S, connect to the VS in response to the vault URL-S, anddeliver a payment result, etc. received from the VS to the user-B; theVS that can connect to the TD in response to the vault URL-B,communicate the vault site-B, or the TD info, etc. with the TD, receivethe payment request, etc. from the TD, connect to the TD in response tothe vault URL-S, deliver a payment order, etc. to a URL vault-B, receivea payment order result, etc. from the URL vault-B, and deliver thepayment result, etc. to the TD; the URL vault-B that can receive thepayment order, etc. from the VS, deliver a money to a collectionaccount-S, and deliver the payment order result, etc. to the VS; and thecollection account-S that can collect the money.

Another aspect is an electronic payment method, comprising: step a) inwhich a TD receives a vault URL-B from a URL medium-B, connects to a VSor a vault site-B in response to the vault URL-B, delivers TD info, etc.to the VS, and delivers a payment request, etc. received from a user-Bto the VS; the VS manages the payment request, etc.; and the TD receivesa vault URL-S from a URL medium-S and connects to the VS in response tothe vault URL-S; step b) in which the VS delivers a payment order, etc.to a URL vault-B; step c) in which the URL vault-B delivers a money to acollection account-S; and step d) in which the collection account-Scollects the money; the URL vault-B delivers a payment order result,etc. to the VS; the VS delivers a payment result, etc. to the TD; andthe TD delivers the payment result, etc. to the user-B.

Another aspect is an electronic charging system, comprising: a URLmedium that can store a vault URL, etc., and deliver the vault URL to aTD; the TD that can receive the vault URL from the URL medium, connectto a VS or a vault site in response to the vault URL, deliver TD info,etc. to the VS, deliver a vault URL PWD, etc. received from a user tothe VS, deliver a vault URL PWD check result, etc. received from the VSto the user, deliver a charge request, etc. received from the user tothe VS, and deliver a charge result, etc. received from the VS to theuser; the VS that can connect to the TD in response to the vault URL,communicate the vault site, or the TD info, etc. with the TD, receivethe vault URL PWD, etc. from the TD, deliver the vault URL PWD checkresult, etc. to the TD, receive the charge request, etc. from the TD,deliver a charge order, etc. to a money supplier, receive a charge orderresult, etc. from the money supplier, and deliver the charge result,etc. to the TD; the money supplier that can receive the charge order,etc. from the VS, deliver a money to a URL vault, and deliver the chargeorder result, etc. to the VS; and the URL vault that can hold the money.

Another aspect is an electronic charging method, comprising: step a) inwhich a TD receives a vault URL from a URL medium, connects to a VS or avault site in response to the vault URL, delivers TD info, etc. to theVS, and delivers a vault URL PWD, etc. received from a user to the VS;the VS delivers a vault URL PWD check result, etc. to the TD; and the TDdelivers the vault URL PWD check result, etc. to the user and delivers acharge request, etc. received from the user to the VS; step b) in whichthe VS delivers a charge order, etc. to a money supplier; step c) inwhich the money supplier delivers a money to a URL vault; and step d) inwhich the URL vault holds the money; the money supplier delivers acharge order result, etc. to the VS; the VS delivers a charge result,etc. to the TD; and the TD delivers the charge result, etc. to the user.

Another aspect is an electronic charge agency system, comprising: a URLmedium that can store a vault URL, etc., and deliver the vault URL to aURL POS; the URL POS that can receive a charge agency request, etc. froma user, receive the vault URL from the URL medium, connect to a VS inresponse to the vault URL, deliver URL POS info, or the charge agencyrequest, etc. to the VS, and deliver a charge agency result, etc.received from the VS to the user; the VS that can connect to the URL POSin response to the vault URL, receive the URL POS info, or the chargeagency request, etc. from the URL POS, deliver a charge order, etc. to amoney supplier, receive a charge order result, etc. from the moneysupplier, and deliver the charge agency result, etc. to the URL POS; themoney supplier that can receive the charge order, etc. from the VS,deliver a money to a URL vault, and deliver the charge order result,etc. to the VS; and the URL vault that can hold the money.

Another aspect is an electronic charge agency method, comprising: stepa) in which a URL POS receives a charge agency request, etc. from auser, receives a vault URL from a URL medium, connects to a VS inresponse to the vault URL, and delivers URL POS info, or the chargeagency request, etc. to the VS; step b) in which the VS connects to theURL POS and delivers a charge order, etc. to a money supplier; step c)in which the money supplier delivers a money to a URL vault; and step d)in which the URL vault holds the money; the money supplier delivers acharge order result, etc. to the VS; the VS delivers a charge agencyresult, etc. to the URL POS; and the URL POS delivers the charge agencyresult, etc. to the user.

Another aspect is an electronic temporary payment system, comprising: aURL medium that can store a vault URL, etc., and deliver the vault URLto a URL POS; and the URL POS that can receive the vault URL from theURL medium, pay temporarily in response to the vault URL, store thevault URL, or a payment result, etc., and deliver the payment result,etc. to a user.

Another aspect is an electronic temporary payment method, comprising:step a) in which a URL medium delivers a vault URL to a URL POS; andstep b) in which the URL POS pays temporarily in response to the vaultURL, stores the vault URL, or a payment result, etc., and delivers thepayment result to a user.

The described technology can provide a simpler and more economical meansof a payment or charging.

The described technology can also provide a simpler and more economicalpayment means or charging means applicable to various transactions.

The described technology can further provide a payment means or chargingmeans that can structurally prevent hacking.

The described technology can further provide a payment method or acharging method that can further reduce fees.

The described technology can further provide a payment method or acharging method that can further create added value.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram and flow diagram of a system that an RF cardcan be charged with money and can pay with money stored in the RF card.

FIG. 2 is a block diagram of a system for paying with money outside ofURL-NFC-CC using URL-NFC-CC, credit card network, and the Internet site.(The FIG. 2 configuration can be compared with the FIG. 7 embodiment.)

FIG. 3 is a flow diagram corresponding to the block diagram of FIG. 2.(The FIG. 3 configuration can be compared with the FIG. 8 embodiment.)

FIG. 4 is a block diagram and flow diagram of a system for paying withmoney outside of an App&SP using the App&SP and App& mobilecommunication network. (FIG. 4 can be the block diagram and flow chartof a WeChat Pay or Alipay. FIG. 4 can be compared with FIG. 7 and FIG. 8embodiments.)

FIG. 5 is a block diagram of a system for paying with money outside aURL medium using the URL medium and the Internet site in a face-to-facetransaction without a user confirmation.

FIG. 6 is a flow diagram corresponding to the block diagram of FIG. 5.

FIG. 7 is a block diagram of a system for paying with money outside aURL medium using the URL medium and the Internet site in a face-to-facetransaction to confirm a user after requesting a payment.

FIG. 8 is a flow diagram corresponding to the block diagram of FIG. 7.

FIG. 9 is a block diagram of a system for paying with money outside aURL medium using the URL medium and the Internet site in a face-to-facetransaction requesting a payment after confirming a user.

FIG. 10 is a flow diagram corresponding to the block diagram of FIG. 9.

FIG. 11 is a block diagram of a system for paying with money outside aURL medium using the URL medium and the Internet site in anon-face-to-face transaction that confirms a user after requesting apayment.

FIG. 12 is a flow diagram corresponding to the block diagram of FIG. 11.

FIG. 13 is a block diagram of a system for paying with money outside aURL medium using the URL medium and the Internet site in anon-face-to-face transaction requesting a payment after confirming auser.

FIG. 14 is a flow diagram corresponding to the block diagram of FIG. 13.

FIG. 15 is a block diagram of a system for paying with money outside aURL medium using two URL mediums and the Internet site in a face-to-facetransaction without a user confirmation.

FIG. 16 is a flow diagram corresponding to the block diagram of FIG. 15.

FIG. 17 is a block diagram of a system for paying with money outside aURL medium by using two URL mediums and the Internet site in aface-to-face transaction to confirm a user.

FIG. 18 is a flow diagram corresponding to the block diagram of FIG. 17.

FIG. 19 is a block diagram of a system for paying with money outside aURL medium by using a URL medium in a face-to-face transaction with aprovisional payment.

FIG. 20 is a flow diagram corresponding to the block diagram of FIG. 19.

FIG. 21 is a block diagram of a system where ‘the outside of a URLmedium’ (URL vault) can be charged with money using the URL medium andthe Internet site in non-face-to-face charging after confirming a user.

FIG. 22 is a flow diagram corresponding to the block diagram of FIG. 21.

FIG. 23 is a block diagram of a system where ‘the outside of a URLmedium’ (URL vault) can be charged with money using the URL medium andthe Internet site in face-to-face charging in which money is paid to athird party and the third party performs charging as an agent.

FIG. 24 is a flow diagram corresponding to the block diagram of FIG. 23.

FIG. 25 is a block diagram of a face-to-face charging system where ‘theoutside of a URL medium’ (URL vault) can be charged with a coupongenerated by transaction, etc. using the URL medium and the Internetsite.

FIG. 26 is a flow diagram corresponding to the block diagram of FIG. 25.

FIG. 27 is a block diagram of a non-face-to-face charging system where‘the outside of a URL medium’ (URL vault) can be charged with a coupongenerated by transaction, etc. using the URL medium and the Internetsite.

FIG. 28 is a flow diagram corresponding to the block diagram of FIG. 27.

DETAILED DESCRIPTION

(Definition and type of a medium) A medium is owned by the user andstores information or means necessary for payment or charging. The RFcard, URL-NFC-CC and App&SP are mediums.

(‘storing money’) For an RF card payment, money is stored on the RFcard, and for a URL-NFC-CC payment, money is stored in an account(CC-account) connected to a system that complies with the standard ofcredit card. In an App&SP's payment, money is stored in an account(App&SP account) connected to the App and the system using the mobilecommunication network.

(System and method for connecting medium and ‘storing money’) The RFcard payment does not require a means of connection. The URL-NFC-CCpayment is connected to the credit card network and the Internet. TheApp&SP's payment connects the medium and ‘storing money’ using asmartphone equipped with App and USIM, and an App & mobile communicationnetwork.

(Credit card network) A credit card network is a communication networkthat can connect a medium (URL-NFC-CC), CC-POS, and ‘CCP server of CCCserver of credit card company.’ The URL-NFC-CC, CC-POS and CCP servercomply with the credit card standard.

(App & mobile communication network) App & mobile communication networkis a communication network that can connect a medium (App&SP: Smartphonewith App and USIM), App POS, and App server through mobile communicationnetwork.

(Relationship between the type of payment path and a medium) Paymentpaths can include: face-to-face tagging (RF card payment), usingdifferent communication networks (URL-NFC-CC payment), incurring fees,requiring special devices, and using ‘the internal operation of themedium’ and ‘external communication networks’ (App&SP payment).Depending on the type of the medium, the composition, cost, andcompetitiveness are different.

(Relationship between payment process and a medium) Payment process canbe divided into payment request process, a user check process, and aremittance process. Depending on a medium, the contents, order, andcompetitiveness of payment process are different.

(Relationship between ‘types of transaction and charging’ and ‘amedium’) a) face-to-face transaction without a user confirmation, b)face-to-face transaction to confirm a user after requesting payment, c)face-to-face transaction to request payment after confirming a user, d)non-face-to-face transaction to confirm a user after requesting payment,e) non-face-to-face transaction requesting payment after confirming auser, f) face-to-face transaction using two mediums without confirming auser, g) face-to face transaction using two mediums after confirming auser, h) face-to-face transaction with a provisional payment, i)non-face-to-face charging after verifying a user, j) face-to-facecharging in which money is paid to a third party and the third partycharges money as an agent, k) face-to-face charging through money(coupon) generated by transactions and the like, l) non-face-to-facecharging which can be charged with money (coupon) generated bytransactions and the like. Depending on the type of media, the types andcompetitiveness of transaction and charging are different.

(Payment process by a medium) a) There is no user check process for anRF card payment. The RF card payment requests payment by tagging an RFcard with an RF card payment machine, which means payment requestprocess. The RF card payment is made by deducting money of the RF card,which means a remittance process. b) for payment of URL-NFC-CC, thecredit card information (CC-info) is transferred to the credit cardcompany's CCP server through the credit card communication network(payment request process), and CC-URL-PWD and CC-URL are transferred tothe credit card company's CCW server (a user check process). The paymentof URL-NFC-CC transfers money from an account (CC-account) linked to thecredit card network to another account (remittance process). c) For anApp&SP payment, a App&SP verifies a App PWD and generates a QR code (auser check process). For the App&SP payment, the App&SP delivers the QRcode to the App Server via an App POS and App& mobile communicationnetwork (payment request process). For the App&SP payment, App&SPtransfers the money from the account (App&SP account) linked to the App&mobile network to another account (a remittance process).

(‘The order of the payment request process and user check process’ by amedium) Since the RF card does not verify a user, there is no user checkprocess. The URL-NFC-CC can change the order of payment request processand user check process. The App&SP can only execute the payment requestprocess after executing the user check process.

Hereinafter, embodiments of the described technology are described indetail with reference to the accompanying drawings. The terms usedherein should be interpreted not in typical or dictionary definitionsbut to comply in concept with the technical matters of the describedtechnology.

The configurations disclosed in the specification and the drawings aremere examples and do not overall represent the technical spirit of thedescribed technology. Therefore, various changes can be made thereto,and equivalents thereof also belong to the scope of the describedtechnology.

URL (Uniform Resource Locator) is the location of a web document or afile in a web server that provides various services.

<The Charging and Payment of a Typical RF Card, Refer to FIG. 1>

(An RF card charging system overview and RF card operation overview)

A user, an RF card charger, an RF card, a payment& RF card chargerequest, an RF card charge, etc. operate organically, so the RF card canbe charged with money.

A user transfers a payment& RF card charge request to an RF cardcharger, and the RF card charger transfers an RF card charge to the RFcard in response to the payment & RF card charge request, so the RF cardcan be charged with money.

(An RF card payment system overview and RF card operation overview)

A user, an RF card payment machine, an RF card, an RF card paymentrequest, an RF card payment, etc. operate organically, so pay with moneystored in the RF card.

A user transmits an RF card payment request to an RF card paymentmachine, and the RF card payment machine transmits an RF card payment toan RF card for a payment.

(Description of RF Card Elements)

An RF card is a medium that can store money as electronic information ortransmit electronic information to the outside.

A user is the person who owns the RF card.

An RF card charger is a device that can receive money and the RF cardcan be charged with money by the RF card charger.

A payment& RF card charge request provides RF card charger with moneyand requests the RF card to be charged with money.

An RF card charge gets the RF card to be charged with money.

An RF card payment machine is a device that can pay with money from theRF card.

An RF card payment request is a request for payment in money of the RFcard.

An RF card payment is to pay with money on the RF card.

(A T-money (a Traffic Card) in Korea) A T-money in Korea is a kind of RFcard. T-money's central account can be charged with money in the form ofelectronic information. The T-money does not distinguish between users.The central account manages the T-money's serial number and money, doesnot verify the user, and deducts the money of the T-money for payment.Since a user is not verified, if a T-money is lost, the balance cannotbe compensated.

(RF card payment features) a) Money is stored inside the RF card. b) Thepayment request process is performed by tagging the RF card with the RFcard payment machine. c) There is no user check process. d) Theremittance process is performed by deducting money from the RF card. e)If the RF card is lost, the balance cannot be compensated. 0 The RF cardpayment do not use confidential information. g) The RF card payment canbe made only at the store that issued the RF card. h) The RF cardpayment cannot be applied to various transactions. i) The RF cardpayment cannot be used for large payment. j) For the RF card payment, itis necessary to make the RF card for each store. k) Money is deliveredto the seller in advance and RF card can be charged with money.

(Comparison of an RF card and a URL medium) a) The RF card stores moneyinternally, but the URL medium stores it externally. b) The RF card hasno secret information, but the URL medium has secret information (vaultURL-PWD). c) If the RF card is lost, the balance of the RF card is notpreserved, but if the URL medium is lost, the balance of the URL mediumis preserved. d) In the case of RF card, it is difficult to apply otherthan face-to-face transactions, but the URL medium can be applied tovarious transactions. e) For a transaction through an RF card, the RFcard must be issued for each store, but for a transaction through a URLmedium, the transaction can be made in many stores through one URLmedium.

(Problems of the RF card payment) a) As money is stored in a smallamount inside the RF card, RF card payment cannot be a universal paymentmethod. b) RF card payment can only be used in stores where the RF cardis charged. c) It is difficult to apply the payment system universally.d) The balance of the lost RF card is not preserved. e) The RF cardpayment cannot be a universal payment method because the RF card paymentcannot be applied to various transactions. f) It is difficult to createadded value.

<A Payment of the Typical URL-NFC-CC, Refer to FIGS. 2 and 3, Which Canbe Compared with FIG. 7 or 8 of the Described Technology.>

(The Payment System and Overview of the URL-NFC CC)

A user, a URL-NFC-CC, a CC-POS, a TD, a CCC server, a CC-account, acollection account, a CC-payment request, CC-info, a CC-URL, a CCW site,TD info, a CC-URL-PWD, a CC-URL-PWD check result, order details, anorder confirmation, a CC-payment order, money, a CC-payment orderresult, and a CC-payment result, etc. operate organically. The paymentsystem of the URL-NFC-CC pays with money outside of the URL-NFC-CC using‘a credit card network that communicates with the URL-NFC-CC and theCC-info’ and ‘the Internet site (CCW site) corresponding to the CC-URL.’

(The URL-NFC-CC Payment Details)

A payment system including: a URL-NFC-CC that can store the CC-info andCC-URL, deliver the CC-info to the CC-POS, and deliver the CC-URL to theTD; a CC-POS that can receive the CC-payment request including the orderdetails from a user, receive the CC-info from the URL-NFC-CC, deliverthe CC-payment request to the CCP server of the CCC server, and deliverthe CC-payment result received from the CCP server to the user; a TDthat can receive the CC-URL from the URL-NFC-CC, connect to the CCWserver of the CCC server in response to the CC-URL, communicate the CCWsite or TD info with the CCW server, deliver the CC-URL-PWD receivedfrom the user to the CCW server, deliver the CC-URL-PWD check result ororder details received from the CCW server to the user, deliver theorder confirmation received from the user to the CCW server, and deliverthe CC-payment result received from the CCW server to the user; a CCCserver that can receive the CC-payment request from the CC-POS, deliverthe CC-payment order to the CC-account, receive the CC-payment orderresult from the CC-account, connect to ‘the CCP server which can deliverthe CC-payment result to the CC-POS’, connect to the TD, communicate theCCW site or TD info with the TD, receive the CC-URL-PWD from the TD,deliver the CC-URL-PWD check result or order details to the TD, receivethe order confirmation from the TD, and include the CCW server which candeliver the CC-payment result to the TD; a CC-account that can receivethe CC-payment order from the CCP server, deliver money to thecollection account, and deliver the CC-payment order result to the CCPserver; and a collection account that can collect the money. and apayment method including: step a) in which the CC-POS receives theCC-payment request including the order details from the user, receivesthe CC-info from the URL-NFC-CC, and delivers the CC-payment request tothe CCP server of the CCC server; and the CCP server manages theCC-payment request; step b) in which the TD receives the CC-URL from theURL-NFC-CC, connects to the CCW server of the CCC server in response tothe CC-URL, communicates the CCW site or TD info with the CCW server,and delivers the CC-URL-PWD received from the user to the CCW server;step c) in which the CCW server delivers the CC-URL-PWD check result ororder details to the TD; step d) in which the TD delivers the CC-URL-PWDcheck result or order details to the user, and delivers the orderconfirmation received from the user to the CCW server; step e) in whichthe CCP server delivers the CC-payment order to the CC-account; step f)in which the CC-account delivers money to the collection account; andthe collection account collects the money; and the CC-account deliversthe CC-payment order result to the CCP server; and step g) in which theCCP server delivers the CC-payment result to the CC-POS; and the CC-POSdelivers the CC-payment result to the user; and the CCW server deliversthe CC-payment result to the TD; and the TD delivers the CC-paymentresult to the user.

(Description of the Elements of URL-NFC CC)

CC-info is information that complies with credit card standards (ISO/IECJTC1/SC17, ISO 7816, ISO 14443, etc.).

CC-info is the basis of payment of URL-NFC-CC, is stored in URL-NFC-CC,and is the basis for creating CC-URL, CC-URL-PWD, CCW server of CCCserver, etc. The CC-info is used in the payment request process andtransmitted to the CCP server of the CCC server through the credit cardnetwork. The CC-info cannot be used in the user check process, andcannot support access to the CCW server of the CCC server.

A CC-URL is a URL that is dependent on CC-info and can support access toa CCW server or CCW site.

The CC-URL is stored in the URL-NFC-CC, used to check a user of CC-info,and used as information to log in to the CCW server, and a CC-URL-PWD isset in the CC-URL. The CC-URL cannot use the credit card network, cannotsupport access to the CCP server, and cannot be used for ‘transactionsthat do not verify the user’, ‘online transactions’, or ‘transactions orcharging using two mediums.’

The URL-NFC-CC is a medium that complies with credit card standards andstores CC-info and CC-URL. The URL-NFC-CC is also a medium in which theCC-URL-PWD is set.

The URL-NFC-CC stores money externally, delivers CC-info to the CCPserver through the credit card network, and passes the CC-URL to the CCWserver through the Internet. The URL-NFC-CC cannot be used for ‘onlinepayment’ and ‘payment and charging using two mediums.’

The URL-NFC-CC is a type of credit card, and because the URL-NFC-CC mustcomply with the standard of credit card, the construction cost andcommission of the URL-NFC-CC system are high.

A user is a subscriber of a credit card and a person who owns theURL-NFC-CC.

A CC-POS is a store sales system that supports the standard of creditcard.

The CC-POS can communicate with CC-info, connect to peripheral devicesthrough a credit card network, and support general credit cards. TheCC-POS cannot communicate with the CC-URL, and does not support onlinepayment and ‘payment and charging using two mediums’.

A CCC server consists of a CCP server that complies with the credit cardstandard, and a CCW server that is subordinate to the CCP server. TheCCC server is a server that oversees the payment of URL-NFC-CC.

The CCC server supports payment but does not support charging. In theCCC server, the payment request process and remittance process use theCCP server, but the user check process uses the CCW server, and the CCPserver and the CCW server communicate with each other to make a payment.The CCC server supports a credit card payment, pays when CC-info, CC-URLand CC-URL-PWD match, and does not support online payment and ‘paymentusing two mediums.’ The construction cost of the system in the CCCserver is high.

A CC-account connects to the credit card network, holds money, and paysin response to the CC-info. The CC-account does not support onlinepayment or ‘payment or charging using two mediums.’

The TD, TD info, and collection account of FIGS. 2 and 3 is differentfrom the described technology's TD, TD info, collection account,communication method, peripheral devices, etc.

A CCW site is the Internet site that is dependent on the CC-info,connects to according to the CC-URL, and is used to identify a user.

The CCW site uses a CC-URL and CC-URL-PWD to determine login. The CCWsite cannot deliver CC-payment request, does not support CC-info, andcannot connect to the CCP server. The CCW server provides the CCW site,and the CC-URL-PWD is set in the CCW site.

A CC-URL-PWD is subordinate to CC-info and CC-URL, and is secretinformation set to log in to the CCW site.

The CC-URL-PWD is set in association with URL-NFC-CC, CC-info, CC-URL,or CCW site. The CC-URL-PWD is not stored in a medium, is memorized bythe user, and is used when the CCW server checks a user.

A CC-URL-PWD check result is the result of checking the CC-URL-PWD.

The CC-payment request, CC-payment order, CC-payment order result, andCC-payment result use credit card-related information, whereas thepayment request, payment order, payment order result, and payment resultof the described technology do not use the credit card-relatedinformation.

The CC-payment request of the URL-NFC-CC payment can include CC-info,but the payment request of the described technology cannot includeCC-info.

(Payment features of URL-NFC-CC) a) Everything related to payment isdependent on the credit card system and is delivered to the CCP serverthrough the credit card network. b) Money is stored outside of theURL-NFC-CC. c) The payment request process delivers CC-info to the CCPserver through the credit card network. d) In the user check process,the CCW server verifies a user using the CC-URL and CC-URL-PWD. e) Theremittance process transfers money outside of URL-NFC-CC to anotheraccount. The outside of URL-NFC-CC means the CC-account. f) The order ofthe payment request process and user check process can be changed. g)The production cost of the medium is high because the medium storesCC-info and CC-URL separately and delivers the CC-info and the CC-URL tothe outside in different ways. h) Since the CC-info requesting a paymentand the CC-URL verifying a user have different paths and attributes, theconstruction cost and operation cost of the system are high. i) Thepayment system of the URL-NFC-CC cannot be charged using the URL-NFC-CC.j) The payment system of the URL-NFC-CC cannot be applied tonon-face-to-face transactions. (KR 10-1751640 and KR 10-1941587 arepatents for face-to-face transactions.) k) The payment system ofURL-NFC-CC cannot pay using two URL-NFC-CCs. l) Since the URL-NFC-CCpayment uses the payment path and system of a credit card, a fee ischarged based on the credit card. m) Since the internet site is not usedwhen requesting a payment, the exposure of the internet site is limited.n) As the exposure of Internet sites is limited, the creation of addedvalue using Internet sites is also limited.

(CC-info) The CC-info complies with the standard of credit card and isthe basis of the URL-NFC-CC, CC-URL, CC-URL-PWD, CCW site, CCC server(CCP server+CCW server), etc. In the described technology, there is noCC-info or a concept comparable thereto.

(Comparison of CC-URL and vault URL) a) The CC-URL is generateddependent on the CC-info, but a vault URL is generated independently. b)The CC-URL is dependent on the CC-info to support a payment, but thevault URL independently supports a payment. c) The CC-URL cannot requestpayment, but vault URL can request payment. d) The CC-URL connects tothe CCW server dependent on CC-info, but the vault URL connects toindependent a VS. e) The CC-URL cannot be used for ‘transactions withouta user verification’, ‘online transactions’, or ‘transactions orcharging using two mediums’, but the vault URL can also support suchtransactions and charging.

(Comparison of a CCW site and a vault site) a) The CCW site is dependenton CC-info, but the vault site is independent. b) The CCW site is setwith the CC-URL PWD dependent on the CC-info, but the vault site is setwith an independent vault URL-PWD. c) The CCW site uses the CC-URL andCC-URL-PWD, which are dependent on CC-info, to determine login, but thevault site uses the independent vault URL and vault URL-PWD to determinelogin. d) The CCW site does not support ‘transactions that do not verifya user’, ‘online transactions’, or ‘transactions or charging using twomediums’, but the vault site can support such transactions or charging.

(Comparison of CC-URL-PWD and vault URL-PWD) a) The CC-URL-PWD is setcorresponding to the CC-URL dependent on CC-info, but the vault URL-PWDis set corresponding to the independent vault URL. b) The CC-URL-PWD isused as secret information to log in to the CCW site subordinate toCC-info, but the vault URL-PWD can be used as secret information to login to the independent vault site. c) In a system using the CC-URL-PWD,payment is made when the CC-URL-PWD, the CC-info and CC-URL match, butin a system using the vault URL-PWD, payment is made when the vaultURL-PWD and the vault URL match. d) A system using the CC-URL-PWD doesnot support ‘transactions that do not verify a user’, ‘onlinetransactions’, or ‘transactions or charging using two mediums’, but asystem using the vault URL-PWD can support such transactions orcharging.

(Comparison of a URL-NFC-CC and URL medium) a) The URL-NFC-CC complieswith credit card standards, but the URL medium does not comply withcredit card standards. b) The URL-NFC-CC stores CC-info that complieswith credit card standards, but the URL medium does not storeinformation that complies with credit card standards. c) In theURL-NFC-CC, the information for requesting payment and the informationfor confirming a user are different, but in the URL medium, the twoinformation are the same. d) The URL-NFC-CC does not support ‘onlinetransactions’ or ‘transactions or charging using two mediums’, but theURL medium can support such transactions or charging.

(Comparison of a CC-POS and URL POS) a) The CC-POS complies with creditcard standards, but the URL POS does not comply with credit cardstandards. b) The CC-POS does not support ‘online transactions’ or‘transactions or charging using two mediums’, but the URL POS cansupport such payment or charging.

(Comparison of CCC sever and VS) a) The CCC server complies with creditcard standards, but the VS does not comply with credit card standards.b) The CCC server is composed of CCP server and CCW server, but the VSis composed of one Web Server. c) In the CCC server, the payment requestprocess and remittance process are executed by the CCP server and theuser check process is executed by the CCW server, but in the VS thethree processes is executed by one server. d) The CCC server does notsupport ‘online transactions’ or ‘transactions or charging using twomediums’, but the VS can support such transactions or charging.

(Comparison of ‘CCW server of CCC server’ and ‘VS’) Both CCW server andVS are web servers based on the Internet, but there are differences asfollows.

a) The CCW server is dependent on the CCP server, but the VS isindependent. b) The CCW server performs only the user check process,which is part of the payment process, but the VS performs the entirepayment process. c) The CCW server communicates with the CCP server foroffline payment, but the VS does not need to communicate with otherservers for offline payment.

(Comparison of CC-account and URL vault) a) CC-account is connected tothe credit card network, but URL vault is not connected to the creditcard network. b) The CC-account cannot be charged using a medium(URL-NFC-CC), but the URL vault can be charged using a medium (the URLmedium).

(Problems with payment of URL-NFC-CC) a) Payment of URL-NFC-CC must bedone using a credit card system. b) The production cost of a medium(URL-NFC-CC) is high. c) The cost of maintaining the system is highbecause the attributes of the path for requesting payment and the pathfor verifying a user are different. d) There is a fee for using thecredit card system. e) Payment of URL-NFC-CC cannot support payment ofonline transactions. f) Payment using two mediums (URL-NFC-CC) cannot besupported. g) Payment of URL-NFC-CC cannot be charged using a medium. h)When paying with a user's money, additional fees for using the creditcard system are incurred. i) Creation of added value is limited.

<Typical app&SP Payment (WeChat Pay or Alipay), Refer to FIG. 4>

(Overview of app&SP's Payment System)

A user, an app-POS, an app&SP, an app server, an app&SP account, acollection account, an app, an app-payment request, an app run order, anapp-PWD, an app-PWD check result, a QR code creation order, a QR code,app-POS info, an app-payment order, money, an app-payment order result,and an app-payment result, etc. operate organically. App&SP's paymentsystem pays with money outside of the medium (app&SP) through the medium(app&SP) and an app& mobile network.

(App&SP Payment Details)

A payment system, including: an app&SP that can install the app, set theapp-PWD, have a USIM, receive the app run order from the user, run theapp, receive the app-PWD from the user, check the app-PWD, deliver theapp-PWD check result to the user, receive the QR code creation orderfrom the user, generate the QR code, deliver the QR code to the app-POS,receive the app-payment result from the app server, and deliver theapp-payment result to the user; an app-POS that can receive theapp-payment request from a user, receive the QR code from the app&SP,connect to the app server, deliver the app-payment request including theapp-POS info or QR code to the app server, and deliver the app-paymentresult received from the app server to the user; an app server that canconnect to the app-POS, receive the app-POS info or app-payment requestfrom the app-POS, deliver the app-payment order to the app&SP accountcorresponding to the QR code, receive the app-payment order result fromthe app&SP account, and deliver the app-payment result to the app-POS orapp&SP; an app&SP account that can receive the app-payment order fromthe app server, deliver money to the collection account, and deliver theapp-payment order result to the app server; and a collection accountwhich can collect the money. and a payment method, including: step a) inwhich the app-POS receives the app-payment request from a user; step b)in which the app&SP receives the app run order from the user, runs theapp, receives the app-PWD from the user, checks the app-PWD, deliversthe app-PWD check result to the user, receives the QR code creationorder from the user, generates the QR code, and delivers the QR code tothe app-POS; step c) in which the app-POS connects to the app server,and delivers the app-payment request including the app-POS info or QRcode to the app server; step d) in which the app server delivers theapp-payment order to the app&SP account corresponding to the QR code;step e) in which the app&SP account delivers money to the collectionaccount; and the collection account collects the money; and the app&SPaccount delivers the app-payment order result to the app server; andstep f) in which the app server delivers the app-payment result to theapp-POS or app&SP; and the app-POS or app&SP delivers the app-paymentresult to the user.

(Description of the Elements of app&SP)

An app is an application software that supports payment or charging.

The app can be provided by the app server and installed on a smart phoneequipped with a USIM. A app-PWD can be set in the app. The app can checkthe app-PWD and store electronic information that can generate a QRcode. The app also can generate the QR code and process the QR code.

A QR code is a user ID and is used as log information of the app server.

The QR code is generated in app&SP after the app-PWD is confirmed. TheQR code is generated whenever payment or charging is required. The QRcode is generated in a medium (app&SP) and delivered to app-POS and appserver. The QR code is used at a different stage from the app-PWD, andis linked to the app&SP account.

A smartphone is a mobile communication terminal, and includes USIM andapp. The smartphone identifies a user with USIM and connects to themobile communication network. The app cannot be used if there is no USIMon the smartphone.

USIM is provided to subscriber of mobile communication network, is usedto identify a user, and supports access to the mobile communicationnetwork. Without USIM, payment or charging is impossible.

The described technology does not require USIM, and there is no conceptcomparable to USIM.

SP info is information on the smartphone including App and USIMinformation. However, the TD info of the described technology does notinclude App or USIM information.

An app&SP is a terminal as well as a medium combined with ‘a smart phoneequipped with USIM’ and ‘an app.’

The app&SP stores app-PWD and electronic information of a QR code,identifies a user with only app-PWD, creates the QR code wheneverpayment is required, delivers the QR code to the app-POS, and performsthe payment request process and user check process.

The electronic information of the QR code is stored in the memory as theelectronic information, and cannot be seen.

A user is a person who owns a smart phone equipped with USIM and owns amedium(app&SP).

An app-POS is a store sales system with an app installed.

The app-POS receives an app-payment request from a user, receives a QRcode from app&SP, connects to the app& mobile network, and transmits anapp-payment request including the QR code to the app server.

App-POS info is information of app-POS.

The app server is the server that manages the app.

The app server provides the app, interlocks with a medium (app&SP) wherethe app is installed, recognizes the QR code as the user ID, does notstore the app-PWD, and does not perform the user check process. The appserver performs a remittance process in response to the QR code andcommunicates with the app&SP, app-POS and the app& mobile network.

The app&SP account is an account that connects to the app& mobilenetwork, holds money, and supports a payment and charging in response toa QR code.

The app run order is a concept of instructing to run an app, and thedescribed technology has no concept comparable to this.

App-PWD is secret information that allows a user to log in to amedium(app&SP).

The app-PWD is set to generate the QR code, which is the user ID of amedium (app&SP), is stored in a medium (app&SP), is not delivered to theapp server, and is used for purposes and processes different from the QRcode.

An app-PWD check result is the result of checking the app-PWD by themedium (app&SP).

The QR code creation order commands the creation of a QR code, and thedescribed technology does not have a concept comparable to this.

The app-payment request, app-payment order, app-payment order result,and app-payment result all use the app, so the payment request, paymentorder, payment order result, and payment result of the describedtechnology are different from them.

The app-payment request of app&SP payment can include a QR code, but thepayment request of the described technology cannot include a QR code.

(Comparison of App and Internet Site)

1) The app is installed and driven on a device such as a smart phone orapp-POS, but the Internet site is driven by a web server

2) App interlocks with devices (such as smartphones or App-POS).However, the internet site interlocks with the web server.

3) The app runs on the device and connects to the App server whenneeded. However, the Internet site links all operations with web server.

4) Since the app is installed on the device, it is difficult to reflectchanges in services in real time, but since the Internet site isprovided by a web server, it is easy to reflect changes in services inreal time.

5) App is highly likely to be hacked. However, the Internet sites areunlikely to be hacked.

6) The information stored and managed by the app is easily leaked whenthe medium (app&SP) where the app is installed is replaced. Informationstored and managed through the Internet site does not leak due to thereplacement of the medium (URL medium).

7) The app runs only on the device where the app is installed, but theInternet site can run on any device with an Internet connection.

8) The app&SP (medium) uses app& mobile network, but the URL medium usesthe Internet.

(app&SP payment features) a) Money is stored outside of app&SP. b) Thepayment request process transmits the QR code to the app-POS and appserver through the app & mobile communication network. c) In the usercheck process, app&SP checks the app-PWD. d) The remittance processtransfers money outside the app&SP to another account. e) The user checkprocess is performed first, and then the payment request process isperformed. (the order cannot be changed) f) The QR code, which is a userID, is generated whenever payment and charging are required. g) Theapp-PWD is used to create a QR code, and the QR code is used to delivermoney. (the app-PWD, which is secret information, and the QR code, whichis user ID, are not used for the same purpose at the same time) h) Asmart phone equipped with app and USIM is required. i) When paying, theuser's own smart phone is required. j) The app and smart phone muststore and manage the app-PWD. k) A user must run the app to form a QRcode. l) There is a high possibility that the app will be hacked. m)When a smart phone is lost, it is easy to leak ‘electronic informationof QR code’ or app-PWD. n) Changes in services or contents cannot bereflected in real time. o) It is difficult to create added value usinginternet sites.

(Comparison of “app-PWD and QR code in FIG. 4” and “vault URL-PWD andvault URL in the described technology”) A QR code is generated, which isuser ID, using the app-PWD, and then the QR code is only used to log into the app server in the FIG. 4. However, the described technology doesnot generate a user ID and uses the vault URL-PWD and the vault URL tolog in to VS.

(Comparison of QR code and vault URL) a) QR code is a user ID for appserver without path attribute, but vault URL is a user ID for VS usingthe Internet path. b) The QR code logs in to the app server alone, butthe vault URL logs in to the vault site with the vault URL-PWD. c)Whenever payment or charging is required, a QR code needs to begenerated, but a vault URL does not need to be generated. d) The QR codeis used after the app-PWD is verified, but the vault URL can be usedwithout confirmation of the password (vault URL-PWD). e) QR code cannotaccess the Internet sites, but vault URL can access Internet sites. f)QR code requires a USIM-equipped smart phone, but the vault URL does notrequire USIM and smart phone.

(Comparison of app-PWD and vault URL-PWD) a) The app-PWD is the secretinformation for logging in to a medium (app&SP) alone, but the vaultURL-PWD is the secret information for logging in to the Internet site(vault site) along with the vault URL, etc. b) The app-PWD is used asinformation to create a QR code, which is a user ID, but the vaultURL-PWD is not used as information to create a user ID. c) The app-PWDis stored in the medium (app&SP), but the vault URL-PWD is not stored inthe medium (URL medium). d) app-PWD is checked by a medium (app&SP), butvault URL-PWD is checked by a server.

(Comparison of app&SP and URL medium) a) The composition of app&SP isthe composition where the app is installed on a smart phone equippedwith USIM. However, the URL medium does not require an app, USIM, orsmart phone. b) app&SP stores app-PWD, but URL medium does not storevault URL-PWD. c) app&SP checks the app-PWD, but URL medium does notcheck the vault URL-PWD. d) app&SP creates a QR code that is a user ID,but URL medium does not create a user ID. e) app&SP needs a function tocommunicate with a user, but URL medium does not have a function tocommunicate with a user.

(Comparison of app&SP's smartphone and the described technology's TD) a)Smart phone requires USIM, but TD does not need USIM. b) The smart phoneneeds to install the app, but TD does not install the app. c) The smartphone contains the function of the medium, but the TD does not containthe function of the medium. d) The smart phone stores the app-PWD andidentifies the user with the app-PWD, but TD does not store the vaultURL-PWD, and the TD cannot verify a user.

(Comparison of app-POS and URL POS) a) App-POS requires an app, but URLPOS does not need an app. b) App-POS receives QR code, but URL POS doesnot receive QR code. c) App-POS delivers the QR code to the app server,but URL POS cannot deliver the QR code.

(Comparison of app server and VS) a) The App server oversees the App,but the VS oversees the Internet site. b) The app server does not storethe app-PWD, but VS stores the vault URL-PWD. c) The app server does notcheck the app-PWD, but VS checks the vault URL-PWD. d) The app serverperforms only the remittance process, but VS performs the paymentrequest process, user check process, and remittance process. e) The appserver verifies users with only QR code, but VS verifies users withvault URL and vault URL-PWD.

(Payment problems using the medium(app&SP) in FIG. 4) a) The cost ofconfiguring the medium(app&SP) is high. b) An app with a risk of hackingis used. c) The user of smartphone and the owner of the smartphone mustbe the same. d) Whenever payment or charging is required, a QR code mustbe generated. e) The smart phone should store the app-PWD. f) Theprocess of executing the app is necessary. g) The order of the usercheck process and payment request process cannot be changed, so itcannot support various transactions. h) Internet sites that can createadded value cannot be used. i) When a smart phone is lost and replaced,there is a high possibility that the app-PWD, etc. will be leaked. j)There is a cost of using the mobile communication network.

A payment method and A charging method of the described technology willbe described with reference to the drawings (from the drawing 5 to thedrawing 28).

<Payment of Face-to-Face Transactions Without User Confirmation, Referto FIGS. 5 and 6>

A URL medium that can store a vault URL, etc., or deliver a vault URL toa URL POS.

A URL POS that can receive a payment request, etc. from a user, receivea vault URL from a URL medium, connect to a VS in response to a vaultURL, deliver URL POS info, or a payment request, etc. to a VS, ordeliver payment result, etc. received from a VS to a user.

A VS that can connect to a URL POS in response to a vault URL, receiveURL POS info, or a payment request, etc. from a URL POS, deliver paymentorder, etc. to a URL vault, receive payment order result, etc. from aURL vault, or deliver payment result, etc. to a URL POS.

A URL vault that can receive payment order, etc. from a VS, delivermoney to a collection account, or deliver payment order result, etc. toa VS.

A collection account that can collect money. The payment system (FIG. 5)can include the URL medium, the URL POS, the VS, the URL vault, and thecollection account, etc.

Step a) in which a URL POS receives a payment request, etc. from a user,receives a vault URL from a URL medium, connects to a VS in response toa vault URL, or delivers URL POS info, or a payment request, etc. to aVS.

Step b) in which a VS connects to a URL POS in response to a vault URLor delivers a payment order, etc. to a URL vault.

Step c) in which a URL vault delivers money to a collection account.

Step d) in which a collection account collects money; a URL vaultdelivers a payment order result, etc. to a VS; a VS deliver a paymentresult, etc. to a URL POS; or a URL POS deliver a payment result, etc.to a user. The payment method (FIG. 6) can include the above steps andother steps.

The payment system (FIG. 5) or the payment method (FIG. 6) pays with themoney of the URL vault (the outside of the URL medium), using a medium(URL medium) and the Internet.

FIGS. 5 and 6 are useful for micropayment.

<Payment of a Face-to-Face Transaction Confirming a User After Receivinga Payment Request, Refer to FIGS. 7 and 8>

A URL medium that can store a vault URL, etc., or deliver a vault URL toa URL POS or a TD.

A URL POS that can receive a payment request, etc. from a user, receivea vault URL from a URL medium, connect to a VS in response to a vaultURL, deliver URL POS info, or a payment request, etc. to a VS, ordeliver a payment result, etc. received from a VS to a user.

A TD that can receive a vault URL from a URL medium, connect to a VS ora vault site in response to a vault URL, deliver TD info, etc. to a VS,deliver a vault URL-PWD, etc. received from a user to a VS, deliver avault URL-PWD check result, or order details, etc. received from a VS toa user, deliver an order confirmation, etc. received from a user to aVS, or deliver a payment result, etc. received from a VS to a user.

A VS that can connect to a URL POS in response to a vault URL, receive aURL POS info, or a payment request, etc. from a URL POS, connect to a TDin response to a vault URL, communicate a vault site, or a TD info, etc.with a TD, receive a vault URL-PWD, etc. from a TD, deliver a vaultURL-PWD check result, or order details, etc. to a TD, receive an orderconfirmation, etc. from a TD, deliver a payment order, etc. to a URLvault, receive a payment order result, etc. from a URL vault, or delivera payment result, etc. to a URL POS or a TD.

A URL vault which can receive a payment order, etc. from a VS, delivermoney to a collection account, or deliver a payment order result, etc.to a VS.

A collection account that can collect money. The payment system (FIG. 7)can include the URL medium, the URL POS, the TD, the VS, the URL vault,and the collection account, etc.

Step a) in which a URL POS receives a payment request, etc. from a user,receives a vault URL from a URL medium, connects to a VS in response toa vault URL, or delivers URL POS info, or a payment request, etc. to aVS; or a VS manages a URL POS info, or a payment request, etc.

Step b) in which a TD receives a vault URL from a URL medium, connectsto a VS or vault site in response to a vault URL, delivers TD info, etc.to a VS, or delivers a vault URL-PWD, etc. received from a user to a VS.

Step c) in which a VS delivers a vault URL-PWD check result, or orderdetails, etc. to a TD; a TD delivers a vault URL-PWD check result, or anorder details, etc. to a user, or delivers an order confirmation, etc.received from a user to a VS; or a VS delivers a payment order, etc. toa URL vault.

Step d) in which a URL vault delivers a money to a collection account.

Step e) in which a collection account collects a money; a URL vaultdelivers a payment order result, etc. to a VS; a VS delivers a paymentresult, etc. to a URL POS or TD; or a URL POS or a TD delivers a paymentresult, etc. to a user. The payment method (FIG. 8) can include theabove steps and other steps.

The payment system (FIG. 7) or the payment method (FIG. 8) pays with themoney of the URL vault(the outside of the URL medium), using a medium (aURL medium) and an interne site (vault site).

<Payment in a Face-to-Face Transaction Receiving a Payment Request AfterConfirming a User, Refer to FIGS. 9 and 10>

A URL medium that can store a vault URL, etc., or deliver a vault URL toa TD or a URL POS.

A TD that can receive a vault URL from a URL medium, connect to a VS orvault site in response to a vault URL, deliver TD info, etc. to a VS,deliver a vault URL-PWD, etc. received from a user to a VS, deliver avault URL-PWD check result, etc. received from a VS to a user, deliver apayment reservation, etc. received from a user to a VS, or deliver apayment result, etc. received from a VS to a user.

A URL POS that can receive a payment request, etc. from a user, receivea vault URL from a URL medium, connect to a VS in response to a vaultURL, deliver URL POS info, or a payment request, etc. to a VS, ordeliver a payment result, etc. received from a VS to a user.

A VS that can connect to a TD in response to a vault URL, communicate avault site, or a TD info, etc. with a TD, receive a vault URL-PWD, etc.from a TD, deliver a vault URL-PWD check result, etc. to a TD, receive apayment reservation, etc. from a TD, connect to a URL POS in response toa vault URL, receive a URL POS info, or a payment request, etc. from aURL POS, deliver a payment order, etc. to a URL vault, receive a paymentorder result, etc. from a URL vault, or deliver a payment result, etc.to a TD or a URL POS.

A URL vault which can receive a payment order, etc. from a VS, delivermoney to a collection account, or deliver a payment order result, etc.to a VS.

A collection account that can collect money. The payment system (FIG. 9)can include the URL medium, the TD, the URL POS, the VS, the URL vault,and the collection account, etc.

Step a) in which a TD receives a vault URL from a URL medium, connectsto a VS or vault site in response to a vault URL, delivers TD info, etc.to a VS, or delivers a vault URL-PWD, etc. received from a user to a VS;a VS delivers a vault URL-PWD check result, etc. to a TD; a TD deliversa vault URL-PWD check result, etc. to a user, or delivers a paymentreservation, etc. received from a user to a VS; or a VS manages apayment reservation, etc.

Step b) in which a URL POS receives a payment request, etc. from a user,receives a vault URL from a URL medium, connects to a VS in response toa vault URL, or delivers URL POS info, or a payment request, etc. to aVS.

Step c) in which a VS delivers a payment order, etc. to a URL vault.

Step d) in which a URL vault delivers a money to a collection account.

Step e) in which a collection account collects a money; a URL vaultdelivers a payment order result, etc. to a VS. a VS delivers a paymentresult, etc. to a TD or URL POS; or a URL POS or TD delivers a paymentresult, etc. to a user. The payment method (FIG. 10) can include theabove steps and other steps.

The payment system (FIG. 9) or the payment method (FIG. 10) pays withthe money of the URL vault (the outside of the URL medium), using amedium (URL medium) and an interne site (vault site).

FIGS. 7, 8, 9, and 10 are useful for transactions with large paymentamounts.

<Payment of a non-face-to-face transaction confirming a user afterreceiving a payment request, refer to FIGS. 11 and 12>

A URL medium that can store a vault URL, etc., or deliver a vault URL toa TD.

A TD that can connect to a SS or a sales site in response to a user's SSaccess order, deliver a payment request including URL medium info, ororder details, etc. received from a user to a SS, receive a vault URLfrom a URL medium, connect to a VS or vault site in response to a vaultURL, deliver TD info, etc. to a VS, deliver a vault URL-PWD, etc.received from a user to a VS, deliver a vault URL-PWD check result, oran order details, etc. received from a VS to a user, deliver an orderconfirmation, etc. received from a user to a VS, or deliver a paymentresult, etc. received from a VS or a SS to a user.

A SS that can connect to a TD, communicate a sales site, or TD info,etc. with a TD, receive a payment request, etc. from a TD, connect to aVS or vault site in response to a URL medium info, deliver SS info, or apayment request, etc. to a VS, or deliver a payment result, etc.received from a VS to a TD.

A VS that can connect to a SS in response to a URL medium info, receivea SS info, or a payment request, etc. from a SS, connect to a TD inresponse to a vault URL, communicate a vault site, or a TD info, etc.with a TD, receive a vault URL-PWD, etc. from a TD, deliver a vaultURL-PWD check result, or an order details, etc. to a TD, receive anorder confirmation, etc. from a TD, deliver a payment order, etc. to aURL vault, receive a payment order result, etc. from a URL vault, ordeliver a payment result, etc. to a SS or a TD.

A URL vault which can receive a payment order, etc. from a VS, delivermoney to a collection account, or deliver a payment order result, etc.to a VS.

A collection account that can collect money. The payment system (FIG.11) can include the URL medium, the TD, the SS, the VS, the URL vault,and the collection account, etc.

Step a) in which a TD connects to a SS or a sales site in response to auser's SS access order, or delivers a payment request including URLmedium info, or order details, etc. received from a user to a SS.

Step b) in which a SS connects to a TD, connects to a VS or vault sitein response to a URL medium info, or delivers SS info, or a paymentrequest, etc. to a VS; or the VS manages a payment request, etc.

Step c) in which a TD receives a vault URL from a URL medium, connectsto a VS or vault site in response to a vault URL, delivers TD info, etc.to a VS, or delivers a vault URL-PWD, etc. received from a user to a VS.

Step d) in which a VS delivers a vault URL-PWD check result, or an orderdetails, etc. to a TD; a TD delivers a vault URL-PWD check result, or anorder details, etc. to a user, or delivers an order confirmation, etc.received from a user to a VS; or a VS delivers a payment order, etc. toa URL vault.

Step e) in which a URL vault delivers money to a collection account.

Step g) in which a collection account collects a money; a URL vaultdelivers a payment order result, etc. to a VS; a VS delivers a paymentresult, etc. to a SS or a TD; a SS delivers a payment result, etc. to aTD; or a TD delivers a payment result, etc. to a user. The paymentmethod (FIG. 12) can include the above steps and other steps.

The payment system (FIG. 11) or the payment method (FIG. 12) pays withthe money of the URL vault (the outside of the URL medium), using amedium (URL medium) and an interne site (vault site).

A payment request can include URL medium info, and URL POS can connectto VS or vault site using URL medium info.

<Payment of a Non-Face-to-Face Transaction Receiving a Payment RequestAfter Confirming a User, Refer to FIGS. 13 and 14>

A URL medium that can store a vault URL, etc., or deliver a vault URL toa TD.

A TD that can receive a vault URL from a URL medium, connect to a VS ora vault site in response to a vault URL, deliver TD info, etc. to a VS,deliver a vault URL-PWD, etc. received from a user to a VS, deliver avault URL-PWD check result, etc. received from a VS to a user, deliver apayment reservation, etc. received from a user to a VS, connect to a SSor sales site in response to a user's SS access order, deliver ‘apayment request including a URL medium info, etc. received from a user’,etc. to a SS, deliver an order #, etc. received from a SS to a user, ordeliver a payment result, etc. received from a SS or VS to a user.

A SS that can connect to a TD, communicate a sales site with a TD,receive a payment request, etc. from a TD, deliver an order #, etc. to aTD, connect to a VS in response to a URL medium info, deliver SS info ora payment request, etc. to a VS, or deliver a payment result, etc.received from a VS to a TD.

A VS that can connect to a TD in response to a vault URL, communicate avault site or TD info, etc. with a TD, receive a vault URL-PWD, etc.from a TD, deliver a vault URL-PWD check result, etc. to a TD, receive apayment reservation, etc. from a TD, connect to a SS, receive a SS infoor a payment request, etc. from a SS, deliver a payment order, etc. to aURL vault, receive a payment order result, etc. from a URL vault, ordeliver a payment result, etc. to a TD or SS, etc.

A URL vault which can receive a payment order, etc. from a VS, delivermoney to a collection account, or deliver a payment order result, etc.to a VS.

A collection account that can collect money. The payment system (FIG.13) can include the URL medium, the TD, the SS, the VS, the URL vault,and the collection account, etc.

Step a) in which a TD receives a vault URL from a URL medium, connectsto a VS or vault site in response to a vault URL, delivers a TD info,etc. to a VS, or delivers a vault URL-PWD, etc. received from a user toa VS; a VS delivers a vault URL-PWD check result, etc. to a TD; a TDdelivers a vault URL-PWD check result, etc. to a user, or delivers apayment reservation, etc. received from a user to a VS; a VS manages apayment reservation, etc.; or a TD connects to a SS or sales site inresponse to a user's SS access order, or delivers ‘a payment requestincluding a URL medium info, etc. received from a user’, etc. to a SS.

Step b) in which a SS can deliver an order #, etc. to a TD, connect to aVS in response to a URL medium info, or deliver a SS info or a paymentrequest, etc. to a VS; or a TD can deliver an order #, etc. to a user.

Step c) in which a VS delivers a payment order, etc. to a URL vault.

Step d) in which a URL vault delivers money to a collection account.

Step e) in which a collection account collects a money; a URL vaultdelivers a payment order result, etc. to a VS; a VS delivers a paymentresult, etc. to a TD or SS; a SS delivers a payment result, etc. to aTD; or a TD delivers a payment result, etc. to a user. The paymentmethod (FIG. 14) can include the above steps and other steps.

The payment system (FIG. 13) or the payment method (FIG. 14) pays withthe money of the URL vault (the outside of the URL medium), using amedium (URL medium) and an interne site (vault site).

A payment request can include the URL medium info, and the SS canconnect to the VS or vault site using the URL medium info.

<Payment of Face-to-Face Transactions Using Two URL Mediums WithoutConfirming a User, Refer to FIGS. 15 and 16>

A URL medium-B that can store a vault URL-B, etc., or deliver a vaultURL-B to a TD.

A URL medium-S that can store a vault URL-S, etc., or deliver a vaultURL-S to a TD.

A TD that can receive a vault URL-B from a URL medium-B, connect to a VSor a vault site-B in response to a vault URL-B, deliver TD info, etc. toa VS, deliver a payment request, etc. received from a user-B to a VS,receive a vault URL-S from a URL medium-S, connect to a VS in responseto a vault URL-S, or deliver a payment result, etc. received from a VSto a user-B.

A VS that can connect to a TD in response to a vault URL-B, communicatea vault site-B or a TD info, etc. with a TD, receive a payment request,etc. from a TD, connect to a TD in response to a vault URL-S, deliver apayment order, etc. to a URL vault-B, receive a payment order result,etc. from a URL vault-B, or deliver a payment result, etc. to a TD.

A URL vault-B which can receive a payment order, etc. from a VS, delivermoney to a collection account-S, or deliver a payment order result, etc.to a VS.

A collection account-S that can collect money. The payment system (FIG.15) can include the URL medium-B, the URL medium-S, the TD, the VS, theURL vault-B, and the collection account-S, etc.

Step a) in which a TD receives a vault URL-B from a URL medium-B,connects to a VS or a vault site-B in response to a vault URL-B,delivers TD info, etc. to a VS, or delivers a payment request, etc.received from a user-B to a VS; or a VS manages a payment request, etc.;or a TD receives a vault URL-S from a URL medium-S, or connects to a VSin response to a vault URL-S.

Step b) in which a VS delivers a payment order, etc. to a URL vault-B.

Step c) in which a URL vault-B delivers money to a collection account-S.

Step d) in which a collection account-S collects money; a URL vault-Bdelivers a payment order result, etc. to a VS; a VS delivers a paymentresult, etc. to a TD; or a TD delivers a payment result, etc. to auser-B. The payment method (FIG. 16) can include the above steps andother steps.

The payment system (FIG. 15) or the payment method (FIG. 16) pays withthe money of the URL vault (the outside of the URL medium), using amedium (URL medium) and an internet site (vault site).

<Payment for Face-to-Face Transactions Using Two URL Mediums AfterConfirming the User-B, Refer to FIGS. 17 and 18>

A URL medium-B that can store a vault URL-B, etc., or deliver a vaultURL-B to a TD.

A URL medium-S that can store a vault URL-S, etc., or deliver a vaultURL-S to a TD.

A TD that can receive a vault URL-B from a URL medium-B, connect to a VSor a vault site-B in response to a vault URL-B, deliver TD info, etc. toa VS, deliver a vault URL-B PWD, etc. received from a user-B to a VS,deliver a vault URL-B PWD check result, etc. received from a VS to auser-B, deliver a payment request, etc. received from a user-B to a VS,receive a vault URL-S from a URL medium-S, connect to a VS or vaultsite-S in response to a vault URL-S, or deliver a payment result, etc.received from a VS to a user-B.

A VS that can connect to a TD in response to a vault URL-B, communicatea vault site-B or a TD info, etc. with a TD, receive a vault URL-B-PWD,etc. from a TD, deliver a vault URL-B-PWD check result, etc. to a TD,receive a payment request, etc. from a TD, connect to a TD in responseto a vault URL-S, deliver a payment order, etc. to a URL vault-B,receive a payment order result, etc. from a URL vault-B, or deliver apayment result, etc. to a TD.

A URL vault-B which can receive a payment order, etc. from a VS, delivermoney to a collection account-S, or deliver a payment order result, etc.to a VS.

A collection account-S that can collect money. The payment system (FIG.17) can include the URL medium-B, the URL medium-S, the TD, the VS, theURL vault-B, and the collection account-S, etc.

Step a) in which a TD receives a vault URL-B from a URL medium-B,connects to a VS or a vault site-B in response to a vault URL-B,delivers TD info, etc. to a VS, or delivers a vault URL-B-PWD, etc.received from a user-B to a VS; a VS delivers a vault URL-B-PWD checkresult, etc. to a TD; a TD delivers a vault URL-B-PWD check result, etc.to a user-B or delivers a payment request, etc. received from a user-Bto a VS; a VS manages a payment request, etc.; or a TD receives a vaultURL-S from a URL medium-S or connects to a VS or vault site-S inresponse to a vault URL-S.

Step b) in which a VS delivers a payment order, etc. to a URL vault-B.

Step c) in which a URL vault-B delivers money to a collection account-S.

Step d) in which a collection account-S receives a money; a URL vault-Bdelivers a payment order result, etc. to a VS; a VS delivers a paymentresult, etc. to a TD; or a TD delivers a payment result, etc. to auser-B. The payment method (FIG. 18) can include the above steps andother steps.

The payment system (FIG. 17) or the payment method (FIG. 18) pays withthe money of the URL vault (the outside of the URL medium), using amedium (URL medium) and an interne site (vault site).

FIGS. 15, 16, 17 and 18 are useful when there is no URL POS.

<Temporary Face-to-Face Payment System, Refer to Drawings 19 and 20>

A URL medium that can store a vault URL, etc., or deliver a vault URL toa URL POS.

A URL POS that can receive a vault URL from a URL medium, pay inresponse to a vault URL, store a vault URL or a payment result, etc., ordeliver a payment result, etc. to a user. The temporary payment system(FIG. 19) can include a URL medium, and a URL POS, etc.

Step a) in which a URL medium delivers the vault URL to the URL POS.

Step b) in which a URL POS pays in response to the vault URL, stores thevault URL or the payment result, etc., or delivers the payment result tothe user. The temporary payment method (FIG. 20) can include the abovesteps and other steps.

The temporary payment system (FIG. 19) or the temporary payment method(FIG. 20) pays temporarily using a medium.

FIGS. 19 and 20 are useful for ‘a case where access to network isdifficult and fast payments are made’ or ‘a case where a payment is maderepeatedly with a small payment amount.’ In the transportation system,access to a network is difficult and fast payment is made.

<Online Charging Receiving a Charge Request After Confirming a User,Refer to FIGS. 21 and 22>

A URL medium that can store a vault URL, etc., or deliver a vault URL toa TD.

A TD that can receive a vault URL from a URL medium, connect to a VS ora vault site in response to a vault URL or deliver TD info, etc. to aVS, deliver a vault URL-PWD, etc. received from a user to a VS, delivera vault URL-PWD check result, etc. received from a VS to a user, delivera charge request, etc. received from a user to a VS, or deliver a chargeresult, etc. received from a VS to a user.

A VS that can connect to a TD in response to a vault URL, communicate avault site or a TD info, etc. with a TD, receive a vault URL-PWD, etc.from a TD, deliver a vault URL-PWD check result, etc. to a TD, receive acharge request, etc. from a TD, deliver a charge order, etc. to a moneysupplier, receive a charge order result, etc. from a money supplier, ordeliver a charge result, etc. to a TD.

A money supplier which can receive a charge order, etc. from a VS,deliver money to a URL vault, or deliver a charge order result, etc. toa VS.

A URL vault that can be charged with money. The charging system (FIG.21) can include the URL medium, the TD, the VS, the money supplier, andthe URL vault, etc.

Step a) in which a TD receives a vault URL from a URL medium, connectsto a VS or vault site in response to a vault URL, delivers TD info, etc.to a VS, or delivers a vault URL-PWD, etc. received from a user to a VS.

Step b) in which a VS delivers a vault URL-PWD check result, etc. to aTD; a TD delivers a vault URL-PWD check result, etc. to a user, ordelivers a charge request, etc. received from a user to a VS; or a VSdelivers a charge order, etc. to a money supplier.

Step c) in which a money supplier delivers money to a URL vault.

Step d) in which a URL vault holds the money; a money supplier deliversa charge order result, etc. to a VS; a VS delivers a charge result, etc.to a TD; or a TD delivers a charge result, etc. to a user. The chargingmethod (FIG. 22) can include the above steps and other steps.

In the charging system (FIG. 21) or the charging method (FIG. 22), theURL vault (the outside of the URL medium) can hold the money, using amedium (URL medium) and an internet site (vault site).

<A Charge Agent System. Face-to-Face Charging System That a Money isPaid to a Third Party and the Third Party Performs Charging Service asan Agent, Refer to FIGS. 23 and 24>

A URL medium that can store a vault URL, etc., or deliver a vault URL toa URL POS.

A URL POS that can receive money or a charge agency request, etc. from auser, receive a vault URL from a URL medium, connect to a VS in responseto a vault URL, deliver URL POS info or a charge agency request, etc. toa VS, or deliver a charge agency result, etc. received from a VS to auser.

A VS that can connect to a URL POS in response to a vault URL, receive aURL POS info or a charge agency request, etc. from a URL POS, deliver acharge order, etc. to a money supplier, receive a charge order result,etc. from a money supplier, or deliver a charge agency result, etc. to aURL POS.

A money supplier that can receive a charge order, etc. from a VS,deliver money to a URL vault, or deliver a charge order result, etc. toa VS.

A URL vault that can be charged with money. The charge agent system(FIG. 23) can include the URL medium, the URL POS, the VS, the moneysupplier, and the URL vault, etc.

Step a) in which a URL POS receives money or a charge agency request,etc. from a user, receives a vault URL from a URL medium, connects to aVS in response to a vault URL, or delivers URL POS info or a chargeagency request, etc. to a VS.

Step b) in which a VS connects to a URL POS or delivers a charge order,etc. to a money supplier.

Step c) in which a money supplier delivers money to a URL vault.

Step d) in which a URL vault is charged with money; a money supplierdelivers a charge order result, etc. to a VS; a VS delivers a chargeagency result, etc. to a URL POS; or a URL POS delivers a charge agencyresult, etc. to a user. The charge agent method (FIG. 24) can includethe above steps and other steps.

In the charge agent system (FIG. 23) or the charge agent method (FIG.24), the URL vault (the outside of the URL medium) can hold the money,using a medium (URL medium) and the Internet.

In the situation of FIGS. 23 and 24, a convenience store, etc. canreceive cash, etc. The convenience store can support charging.

<A Offline Coupon Charge System. Offline Charging Using CouponsGenerated by Transactions, Etc., Refer to FIGS. 25 and 26>

A URL medium that can store a vault URL, etc., or deliver a vault URL toa URL POS.

A URL POS that can receive a coupon charge request, etc. from a user,receive a vault URL from a URL medium, connect to a VS in response to avault URL, deliver a URL POS info or coupon charge request, etc. to aVS, or deliver a coupon charge result, etc. received from a VS to auser.

A VS that can connect to a URL POS in response to a vault URL, receive aURL POS info or coupon charge request, etc. from a URL POS, deliver acoupon to a URL vault, or deliver a coupon charge result, etc. to a URLPOS.

A URL vault that can collect a coupon (money). The offline coupon chargesystem (FIG. 25) can include the URL medium, the URL POS, the VS, andthe URL vault, etc.

Step a) in which a URL POS receives a coupon charge request, etc. from auser, receives a vault URL from a URL medium, connects to a VS inresponse to a vault URL, or delivers a URL POS info or coupon chargerequest, etc. to a VS.

Step b) in which a VS connects to a URL POS or delivers a coupon to aURL vault.

Step c) in which a URL vault collects a coupon.

Step d) in which a VS delivers a coupon charge result, etc. to a URLPOS; or a URL POS delivers a coupon charge result, etc. to a user. Theoffline coupon charge method (FIG. 26) can include the above steps andother steps.

In the offline coupon charge system (FIG. 25) or the offline couponcharge method (FIG. 26), the URL vault (the outside of the URL medium)can hold the money (coupon), using a medium (URL medium) and theInternet.

FIGS. 25 and 26 are useful for using a charging service by using couponsgenerated in offline transactions. The coupon charge request can includecoupons generated in transactions.

<A Online Coupon Charge System. Online Charging Using Coupons Generatedby Transactions, Etc., Refer to FIGS. 27 and 28>

A URL medium that can store URL medium info, etc., or deliver a URLmedium info to a user.

A TD that can deliver ‘the coupon charge request including a URL mediuminfo, etc. received from a user’, etc. to a SS, or deliver a couponcharge result, etc. to a user.

A SS that can receive a coupon charge request, etc. from a TD, connectto a VS or vault site in response to a URL medium info, deliver a SSinfo or coupon charge request, etc. to a VS, or deliver a coupon chargeresult, etc. received from a VS to a TD.

A VS that can connect to a SS in response to a URL medium info, receivea SS info or coupon charge request, etc. from a SS, deliver a coupon toa URL vault, or deliver a coupon charge result, etc. to a SS.

A URL vault that can collect a money. The online coupon charge system(FIG. 27) can include the URL medium, the TD, the SS, the VS, and theURL vault, etc.

Step a) in which a TD delivers a ‘coupon charge request including URLmedium info, etc.’, etc. received from a user to a SS.

Step b) in which a SS connects to a VS or vault site in response to aURL medium info, or delivers a SS info or coupon charge request, etc. toa VS.

Step c) in which a VS connects to a SS or delivers money to a URL vault.

Step d) in which a URL vault collects money.

Step e) in which a VS delivers a coupon charge result, etc. to a SS.

Step f) in which a SS delivers a coupon charge result, etc. to a TD. Orstep g) in which a TD delivers a coupon charge result to a user. Theonline coupon charge method (FIG. 28) can include the above steps andother steps.

In the online coupon charge system (FIG. 27) or the online coupon chargemethod (FIG. 28), the URL vault (the outside of the URL medium) can holdthe money (coupon), using a medium (URL medium) and an internet site(vault site).

A coupon charge request can include a URL medium info, or coupon, etc.

FIGS. 27 and 28 are useful for using charging services by using couponsgenerated in online transactions.

(A URL medium payment process) In a payment request process, “a URLmedium payment process” delivers a vault URL or related information to aVS through the Internet. In user check process, a URL medium paymentprocess checks a user with a vault URL or a vault URL-PWD, etc.. Inremittance process, a URL medium payment delivers money from a URL vaultto a collection account.

<About the Terms of the Described Technology>

(URL medium) A URL medium is a kind of medium storing a vault URL. A URLmedium-B or a URL medium-S is a kind of URL medium. A URL medium-B'svault URL-B and a URL medium-S's vault URL-S are different.

A URL medium can further store URL medium info, or representativeelectronic information, etc. For a URL medium, vault URL-PWD or otherscan be set. A URL medium does not store money internally, and canprovide a vault URL, URL medium info, or representative electronicinformation, etc. to the outside. A URL medium can support access to aVS or a vault site, pay with money of a URL vault, or charge money to aURL vault. A URL medium does not store a vault URL-PWD internally, doesnot have a function to check a vault URL-PWD, or can be used inconjunction with a collection account when collecting money. A URLmedium does not store ‘a CC-info ’ or ‘a QR code’.

(URL medium info, Representative electronic information) URL medium infois non-electronic information (e.g., serial number, etc.) correspondingto a URL medium or a vault URL, or can be displayed on the surface of aURL medium, etc.. URL medium info can support connecting to a VS or avault site. Representative electronic information is electronicinformation (e.g., serial number, etc.) corresponding to a URL medium ora vault URL. Representative electronic information can support access toa VS or a vault site.

(User) A user owns a URL medium and a user-B owns a URL medium-B.

(URL vault) A URL vault can store money corresponding to a URL medium.Examples of a URL vault can include a bank account or a coupon store,etc.

A URL vault can charge money or transfer money or balance information,etc. to the outside.

(Vault site) A vault site is an interne site that can support payingwith money of a URL vault or charging money into a URL vault. A vaultsite-B or a vault site-S is a kind of vault site.

A vault site can support an access of a vault URL, URL medium info, orrepresentative electronic information. A vault site can support a vaultURL-PWD, can support logging in with a vault URL or a vault URL-PWD,etc., can support various transactions, charging, or additionalservices, etc., and can include advertisements.

(VS=Vault Server) A VS is a kind of web server that supports paying withmoney of a URL vault or charging money into a URL vault. A VS canexercise overall control everything needed for payment or charging.

A VS can provide a vault site or additional services, store a vaultURL-PWD, and determine login with a vault URL or a vault URL-PWD, etc. AVS can execute “payment request process”, “user check process”, and“remittance process”, can support various transactions or charging,etc., and can communicate with an external server, etc. A VS can receivemoney (coupon, etc.) from outside, and charge money into a URL vault,etc.

(Vault URL) A vault URL is a kind of URL that can support connecting toa VS or a vault site. A vault URL-B or a vault URL-S is a kind of vaultURL.

A vault URL can support access to other things, and can includerepresentative electronic information, etc. A vault URL can be stored ina URL medium in the form of electronic information or images, etc., andcan be used as a user ID. A vault URL can be used with a vault URL-PWD,etc., and can also be used when collecting money.

(Money supplier) A money supplier can supply money, etc. to a URL vault,etc.. A money supplier includes a bank account, a securities account, acredit card, a collection account, or a VS, etc. One URL vault can be amoney supplier for another URL vault.

A money supplier can automatically transfer money to a URL vault, etc.

(Collection account) A collection account can receive money, etc. Acollection account includes a bank account, etc., and a collectionaccount-S is a collection account corresponding to a vault URL-S.

(TD=Terminal Device) A TD is a terminal device that has functions tocommunicate with a URL medium, communicate information with a user,connect to the Internet, or other functions.

A smart phone is a representative TD, and a PC, a wall pad, or a TV witha device capable of communicating with a URL medium can also be a TD.

A TD of the described technology does not require a USIM or a app. OneTD can connect to a sales site (SS) and another TD can connect to a VSor a vault site for payment, and can act as a URL POS.

(TD info or TD information) TD info is information held by a TD, such asa TD's IP, a OS serial number, a MAC address, or an International MobileEquipment Identity (IMEI). TD info can be transmitted to the outside, orcan be used as information to confirm a TD, or a user, etc.

(URL POS) A URL POS or a URL POS system is a store sales system or apoint-of-sale information management system that can manage salesinformation, etc., consisting of sales devices, or sales functions, etc.The URL POS can consist of an ordering device, a charging device, acredit card payment device, a device that communicates with a URLmedium, a balance check device (a device that checks a balance of a URLvault), or a management computer. The URL POS can include a SS(=SalesServer) or an operating software. The URL POS can include a ticketmachine, a washing machine, or a car wash with a URL medium payment.

A URL POS can use internal menus or VS menus, and can deliverinformation of payment, charging, or system operating to a VS.

(URL POS info or URL POS information) A URL POS info is information thata URL POS holds, such as a URL POS IP, a OS serial number, a MACaddress, or a device identification information (IMEI: InternationalMobile Equipment Identity). A URL POS info can be transmitted to theoutside, or can be used as information to check a URL POS or an operatorof the URL POS.

(Money) Money has economic value. Money can include a coupon, etc.issued by a VS, or a SS, etc.

(Vault URL-PWD) A vault URL-PWD is secret information that can supportthe payment with money of a URL vault or charging money into a URLvault. A vault URL-PWD can be set in association with a URL medium, avault site, or a vault URL, etc.

A vault URL-PWD can be remembered by a user, used as login information,and used as information to confirm a user.

(Vault URL-PWD check result) A vault URL-PWD check result is a result ofchecking a vault URL-PWD, or a vault URL, TD info, etc.

(Comparison between a CCC server and a app server and a VS) A CCC serveris composed of a CCP server that supports “payment request process” and“remittance process” in response to CC-info, and a CCW server thatsupports “user check process” in response to CC-URL. A CCC serversupports payment with money of a CC Account. A CCC server does notsupport charging. A app server is a kind of app server that supports anapp&SP or an app, recognizes a QR code as an user ID, pays with money ofan App&SP account , and supports charging money into an App&SP account.A VS is a kind of web server that supports a URL medium, or a vaultsite, etc., pays with money of a URL vault, and charges money into a URLvault.

An order # is a number representing an order. An order # can be used fordesignating order details, etc.

Order details can include item information or price information, etc..The order details can be included in a payment request.

An order confirmation confirms order details, etc., and can includerelevant information.

A payment reservation is to make a reservation for payment. The paymentreservation can include related information.

A payment request is a request for payment with money of a URL vault,and can include related information.

A payment request can include URL medium info, representative electronicinformation, or order details, etc.. The payment request does notinclude a CC-info or a QR code.

A payment order is an order to pay with money of a URL vault, and caninclude related information.

A payment order result is a result of executing a payment order, and caninclude related information.

A payment result is a result of executing a payment request, can includerelated information, and can be delivered through a vault site or a textmessage.

A charge request is a request to charge money into a URL vault, caninclude related information (URL medium info, representative electronicinformation, or money information, etc.), and can be automaticallyexecuted by presetting.

A charge result is a result of charging, can include relatedinformation, and can be delivered through a vault sites or a textmessage.

A charge order is an order to charge money into a URL vault, and caninclude related information.

A charge order result is a result of executing a charge order and caninclude related information.

A charge agency request is a request for a third party to charge moneyinto a URL vault, and can include “delivering money to the third party”and include related information.

A charge agency result is a result of executing a charge agency request,can include related information, and can be delivered through a vaultsite or a text message.

For the same purpose, the second access can occur after the firstaccess.

A access order is an order to access, and can include relatedinformation.

A sales site is an internet site that sells goods or services, etc.

An advertisement means all information or contents other thaninformation related to payment or charging.

(Features and advantages of a URL medium payment) a) A URL mediumpayment stores money to a URL vault. b) A URL medium payment can delivera vault URL or information, etc. to a vault site or a VS in “paymentrequest process”. c) A URL medium payment can deliver a vault URL-PWD,etc. to a VS in “user check process”. d) A URL medium payment transfersmoney of a URL vault to a collection account in “remittance process” e)In a URL medium payment, “payment request process” and “user checkprocess” can be exchanged. f) Since a URL medium payment uses only onetype of information (vault URL), the production cost of medium (URLmedium) is low. g) In a URL medium payment, a payment request path and auser check path are different, but the information (a vault URL) on thepath used is the same. h) A URL medium can charge money to a URL vault.i) A URL medium payment can support various transactions. j) For URLmedium payments, the commission is cheap or there is no commission. k) AURL medium payment can structurally prevent hacking. 1) For URL mediumpayment, a balance is protected even if a URL medium is lost. m) A URLmedium payment is advantageous in creating added value using an internetsite because the entire payment process (“payment request process”,“user check process” and “remittance process”) uses an internet site. n)A URL medium payment can support payment without a user's smart phone.o) For a URL medium payment, there is no information leakage even if asmart phone is lost. p) A URL medium payment can reflect changes inservice or content in real time. q) A URL medium payment does notrequire a credit card system or an app.

Explanation of the Sign

110-1, 110-2, 110-3, 110-4: RF card (Medium for RF Card Payment)

120-1, 120-2, 120-3, 120-4: User

130-1, 130-2: RF Card Charger

140-3, 140-4: RF Card Payment Machine

210, 310: URL-NFC-CC (=Medium for URL-NFC-CC payment)

220, 320: User

230, 330: CC POS

240, 340: TD

250, 350: CCC Server(=CCP Server +CCW Server)

270, 370: Collection Account

280, 380: CC Account

410-1, 410-2: App&SP (=Medium for App&SP Payment)

420-1, 420-2: User

430-1, 430-2: App POS

450-1, 450-2: App Server

470-1, 470-2: Collection Account

480-1, 480-2: App&SP Account

510, 610, 710, 810, 910, 1010, 1110, 1210, 1310, 1410, 1510B, 1510S,1610B, 1610S, 1710B, 1710S, 1810B, 1810S, 1910, 2010, 2110, 2210, 2310,2410, 2510, 2610, 2710, 2810: URL Medium, or URL Medium-B, or URLMedium-S

520, 620, 720, 820, 920, 1020, 1120, 1220, 1320, 1420, 1520B, 1620B,1720B, 1820B, 1920, 2020, 2120, 2220, 2320, 2420, 2520, 2620, 2720,2820: User, or User-B

530, 630, 730, 830, 930, 1030, 1130, 1230, 1330, 1430, 1930, 2030, 2330,2430, 2530, 2630, 2730, 2830: URL POS or SS

740, 840, 940, 1040, 1140, 1240, 1340, 1440, 1540, 1640, 1740, 1840,2140, 2240, 2740, 2840: TD

550, 650, 750, 850, 950, 1050, 1150, 1250, 1350, 1450, 1550, 1650, 1750,1850, 2150, 2250, 2350, 2450, 2550, 2650, 2750, 2850: VS

2160, 2260, 2360, 2460: Money Supplier

570, 670, 770, 870, 970, 1070, 1170, 1270, 1370, 1470, 1570S, 1670S,1770S, 1870S: Collection Account, or Collection Account-S

580, 680, 780, 880, 980, 1080, 1180, 1280, 1380, 1480, 1580B, 1680B,1780B, 1880B, 2180, 2280, 2380, 2480, 2580, 2680, 2780, 2880: URL vault,or URL vault-B

What is claimed is:
 1. An electronic payment system, comprising: a uniform resource locator (URL) medium configured to store a vault URL, and transmit the vault URL to a URL point of sale (POS) system or a terminal device (TD); the URL POS system configured to receive a payment request from a user, receive the vault URL from the URL medium, connect to a vault server (VS) in response to receiving the vault URL, transmit URL POS information or the payment request to the VS, and provide a payment result received from the VS to the user; the TD configured to receive the vault URL from the URL medium, connect to the VS or a vault site in response to receiving the vault URL, transmit TD information to the VS, transmit a vault URL password (PWD) received from the user to the VS, provide a vault URL PWD check result or order details received from the VS to the user, transmit an order confirmation received from the user to the VS, and provide the payment result received from the VS to the user; the VS configured to connect to the URL POS system in response to receiving the vault URL, receive the URL POS information or the payment request from the URL POS system, connect to the TD in response to receiving the vault URL, communicate the vault site or the TD information with the TD, receive the vault URL PWD from the TD, transmit the vault URL PWD check result or the order details to the TD, receive the order confirmation from the TD, transmit a payment order to a URL vault, receive a payment order result from the URL vault, and transmit the payment result to the URL POS system or the TD; the URL vault configured to receive the payment order from the VS, transfer money to a collection account, and transmit the payment order result to the VS; and the collection account configured to collect the money.
 2. An electronic payment method, comprising: at a uniform resource locator (URL) point of sale (POS) system, receiving a payment request from a user, receiving a vault URL from a URL medium, connecting to a vault server (VS) in response to receiving the vault URL, and transmitting URL POS information or the payment request to the VS, wherein the VS manages the URL POS information or the payment request; at a terminal device (TD), receiving the vault URL from the URL medium, connecting to the VS or a vault site in response to receiving the vault URL, transmitting TD information to the VS, and transmitting a vault URL password (PWD) received from the user to the VS; at the VS, transmitting a vault URL PWD check result or order details to the TD, wherein the TD provides the vault URL PWD check result or the order details to the user, and transmits an order confirmation received from the user to the VS, and wherein the VS transmits a payment order to a URL vault; at the URL vault, transferring money to a collection account; and at the collection account, collecting the money, wherein the URL vault transmits a payment order result to the VS, wherein the VS transmits a payment result to the URL POS system or the TD, and wherein the URL POS system or the TD provides the payment result to the user.
 3. An electronic payment system, comprising: a uniform resource locator (URL) medium configured to store a vault URL and transmit the vault URL to a terminal device (TD) or a URL point of sale (POS) system; the TD configured to receive the vault URL from the URL medium, connect to a vault server (VS) or a vault site in response to receiving the vault URL, transmit TD information to the VS, transmit a vault URL password (PWD) received from a user to the VS, provide a vault URL PWD check result received from the VS to the user, transmit a payment reservation received from the user to the VS, and provide a payment result received from the VS to the user; the URL POS system configured to receive a payment request from the user, receive the vault URL from the URL medium, connect to the VS in response to receiving the vault URL, transmit URL POS information or the payment request to the VS, and provide the payment result received from the VS to the user; the VS configured to connect to the TD in response to receiving the vault URL, communicate the vault site or the TD information with the TD, receive the vault URL PWD from the TD, transmit the vault URL PWD check result to the TD, receive the payment reservation from the TD, connect to the URL POS system in response to receiving the vault URL, receive the URL POS information or the payment request from the URL POS system, transmit a payment order to a URL vault, receive a payment order result from the URL vault, and transmit the payment result to the TD or the URL POS system; the URL vault configured to receive the payment order from the VS, transfer money to a collection account, and transmit the payment order result to the VS; and the collection account configured to collect the money.
 4. An electronic payment method, comprising: at a terminal device (TD), receiving a vault URL from a URL medium, connecting to a vault server (VS) or a vault site in response to receiving the vault URL, transmitting TD information to the VS, and transmitting a vault URL password (PWD) received from a user to the VS, wherein the VS transmits a vault URL PWD check result to the TD, wherein the TD provides the vault URL PWD check result to the user, and transmits a payment reservation received from the user to the VS, and wherein the VS manages the payment reservation; at a URL point of sale (POS) system, receiving a payment request from the user, receiving the vault URL from the URL medium, connecting to the VS in response to receiving the vault URL, and transmitting URL POS information or the payment request to the VS; at the VS, transmitting a payment order to a URL vault; at the URL vault, transferring money to a collection account; and at the collection account, collecting the money, wherein the URL vault transmits a payment order result to the VS, wherein the VS transmits a payment result to the TD or the URL POS system, and wherein the TD or the URL POS system provides the payment result to the user.
 5. An electronic payment system, comprising: a uniform resource locator (URL) medium configured to store a vault URL and transmit the vault URL to a terminal device (TD); the TD configured to connect to a sales site (SS) in response to receiving a user's SS access order, transmit a payment request including URL medium information or order details received from the user to the SS, receive the vault URL from the URL medium, connect to a vault server (VS) or a vault site in response to receiving the vault URL, transmit TD information to the VS, transmit a vault URL password (PWD) received from the user to the VS, provide a vault URL PWD check result or the order details received from the VS to the user, transmit an order confirmation received from the user to the VS, and provide a payment result received from the VS or the SS to the user; the SS configured to connect to the TD, communicate the sales site or TD information with the TD, receive the payment request from the TD, connect to the VS or the vault site in response to receiving the URL medium information, transmit SS information or the payment request to the VS, and transmit the payment result received from the VS to the TD; the VS configured to connect to the SS in response to receiving the URL medium information, receive the SS information or the payment request from the SS, connect to the TD in response to receiving the vault URL, communicate the vault site or TD information with the TD, receive the vault URL password (PWD) from the TD, transmit the vault URL PWD check result or the order details to the TD, receive the order confirmation from the TD, transmit a payment order to a URL vault, receive a payment order result from the URL vault, and transmit the payment result to the SS or the TD; the URL vault configured to receive the payment order from the VS, transfer money to a collection account, and transmit the payment order result to the VS; and the collection account configured to collect the money.
 6. An electronic payment method, comprising: at a terminal device (TD), connecting to a sales site (SS) in response to receiving a user's SS access order, and transmitting a payment request including URL medium information or order details received from the user to the SS; at the SS, connecting to the TD, connecting to a vault server (VS) or a vault site in response to receiving the URL medium information, and transmitting SS information or the payment request to the VS, wherein the VS manages the payment request; at the TD, receiving a vault URL from a URL medium, connecting to the VS or a vault site in response to receiving the vault URL, transmitting TD information to the VS, and transmitting a vault URL password (PWD) received from the user to the VS; at the VS, transmitting a vault URL PWD check result or the order details to the TD, wherein the TD provides the vault URL PWD check result or the order details to the user, and transmits an order confirmation received from the user to the VS, and wherein the VS transmits a payment order to a URL vault; at the URL vault, transferring money to a collection account; and at the collection account, collecting the money, wherein the URL vault transmits a payment order result to the VS, wherein the VS transmits a payment result to the SS or the TD, wherein the SS transmits the payment result to the TD, and wherein the TD provide the payment result to the user. 